r? @Mark-Simulacrum

(rust_highfive has picked a reviewer for you, use r? to override)

Do you have some way of confirming this doesn't break anything? I'm a bit worried that they will not be redundant somewhere (e.g., on a prior version)... I don't know that we have tests for this file, either.

If they're harmless I am inclined to leave them in.

@Mark-Simulacrum The current version of rust-lldb (and so the script shipped with rust 1.47) doesn't use appropriate pretty-printers because of these backslashes, at least on my machine (macOS 10.15.6, with lldb-1200.0.32.1). But with this patch, rust-lldb works fine. So this PR is not just a cleanup, but a bug-fix. Actually, these backslashes were added accidentally when I converted LLDB command-line arguments to lldb_commands file.

It would be great if someone else tests it. And there really should be some tests for rust-lldb with different LLDB versions.

Ok, given that they were recently added seems fine to remove.

@bors r+ rollup=never

📌 Commit 4f792d6 has been approved by Mark-Simulacrum

⌛ Testing commit 4f792d6 with merge be719d1...

☀️ Test successful - checks-actions, checks-azure
Approved by: Mark-Simulacrum
Pushing be719d1 to master...